New fields for Central Postcode Directory in CDR Processing Output

The CDR Processing output now includes additional fields to support enhanced reporting and data completeness. The following fields have been added:

• AA2024

• AA2024NAME

• SETTLEMENT15BAND

• TTWA2011CODE

• TTWA2011NAME

• COUNTY

These fields are available in the CDR processing output and can be used in downstream reporting and data integrations. Each field is provided as an optional text value, allowing you to adopt the new data without impacting existing processes.

Collecting CDR data

Minimum and maximum guided learning hours

This release introduces new fields to support the 2026/27 CDR changes to how guided learning hours are recorded and reported.

Staff can now record minimum and maximum guided learning hours for a programme:

• Two new fields, Minimum Guided Learning Hours and Maximum Guided Learning Hours, are available on the Curriculum Details screen under the CDR tab for UIO Details.

• These fields have also been added to the CDR return output and web services.

These changes ensure your data collection, reporting, and integrations are aligned with the updated 2026/27 CDR requirements.

Collecting CDR data

Mapping for Auto-population of Guided Learning Hours

Guided learning hours are now automatically populated when you select a qualification for a programme.

When you choose a Qualification Number on the CDR tab of UIO Details, the corresponding guided learning hours value is automatically filled.

This change reduces manual data entry and helps ensure guided learning hours are recorded accurately and consistently for CDR reporting.

Not applicable

VCSE Learning

Staff can now record VCSE (Voluntary, Community and Social Enterprise) Learning information directly in the user interface.

Two new dropdown lists are available in Learner Details > Other Details:

• VCSE Learning (Community Learning)

• VCSE Learning Category (Community Learning Category)

Note that these fields have also been added to the CDR return output.

These additions make it easier to capture VCSE learning information consistently and support accurate reporting and data management.

SEN Statement

Staff can now record a learner’s Special Educational Needs (SEN) Statement directly in the user interface.

A new SEN Statement drop-down list is available in Learner Details > Other Details, making it easier to capture and manage SEN information consistently. Note that this fields has also been added to the CDR return output.

This update supports clearer data entry and helps ensure SEN details are recorded accurately for reporting and operational use.

Collecting CDR data

IND_GROSS - Output (Values) and CDR_REPORTING

A new IND_GROSS field is now available in the CDR_REPORTING table and the CDR Processing output. The IND_GROSS field identifies the learner’s primary enrolment for CDR purposes. It defaults to 0 and is set to 1 when the enrolment meets the required criteria.

How IND_GROSS is determined

For each learner, a single enrolment is selected based on the following characteristics, applied in order of priority:

1. Mode of attendance (STUDENT_MOA)

   • Full‑time (MOA 01 and MOA 20), then

   • Part‑time (all other MOA codes)

2. Regulated (descending)

3. Total student hours (TOTAL_S_HRS) (descending)

4. Level (LVL) (descending)

5. No exclusions are applied to this selection.

When IND_GROSS is set to 1

The IND_GROSS value is set to 1 when all of the following apply:

• FEI_1 = 1 (see the CDR Data Dictionary and specifications for details)

• Progress Status is any value other than T – Transfer

This update supports clearer identification of gross learners in CDR reporting and processing.

CDR field name updates for 2026/27

Several enrolment detail field labels have been updated in the CDR Processing output to align with current CDR requirements.

The following label changes have been applied:

• PROG_PATHWAY is now labelled PROG_ROUTE

• PROG_YEAR is now labelled PROG_ROUTE_DATE

• HLA_PATHWAY is now labelled PATHWAY

These updated labels are reflected in the CDR_REPORTING table and the CDR Processing output.

Where you’ll see the changes:

• Programme Route and Programme Route Date are set at programme enrolment level in Learner Enrolment > Learner Details.

• Pathway is set at qualification enrolment level.

In the CDR output:

• PROG_ROUTE and PROG_ROUTE_DATE appear on lines 31 and 32

• PATHWAY appears on line 167

This update ensures field names are consistent and aligned with CDR reporting expectations.

Validation priority updates for 2026/27

Validation priorities have been updated to align with the 2026/27 CDR specification, helping you understand how validations are classified across CDR tools and reports.

Updated priority terminology

The following priority labels are now used:

• Early Monitoring Priority (EMP) – replaces Weekly

• Monthly Priority (MP) – replaces Monthly

A validation can be assigned both EMP and MP, where applicable.

User interface updates

These changes are reflected across the CDR validation tools:

In Validation Manager, the Weekly Priority field is now labelled Early Monitoring Priority.

In the CDR Error Surfer, priority filters have been renamed to reflect the new terminology:

• Early Monitoring and Monthly Only

• Early Monitoring Only

• Monthly Only

Reporting updates

New columns have been added to support the updated priorities:

• EMP

• MP

These columns are available in Data Miner, CDR reports, validation output summaries, and associated reports.

This update ensures validation priorities are clearly presented and consistent with the latest CDR requirements.

New validation rules

Nine new CDR validation rules have been added to support updated data checks.

Staff can view the new validation rules in both Validation Manager and Error Surfer. The following rules are included:

• Validation rules 26, 186, 187, 188, 201, and 219

These rules are also available in Error Surfer.

This update helps ensure your CDR data is validated consistently in line with the latest requirements.

We’ve made a number of updates to existing validation rules to improve clarity, consistency and accuracy as follows:

• New valid value added to Validation Rule 35.

• Correction to rule logic in Validation Rule 159 to remove an incorrect full achievement outcome.

• Terminology updates across several rules to replace Programme Pathway with Programme Route where applicable.

• Improved wording in rule names, descriptions and error messages to use clearer, more consistent language. For example, missing instead of null, and enrolment instead of learner.

• Exam board grade validation enhanced by including the AWARD value where relevant.

• Spelling standardised from Dependents to Dependants across affected rules.

• Validation rules 118, 127, 130, 138, 167, 168, 171, 172, 250, 313, 331, and 340 have been updated.

• The monthly priority for Validation rule 38 is now set to Y.

• Validation rule 184 has been removed as it is redundant due to Validation rule 187.

These changes mainly affect Traineeship enrolments (Student Type 97) and validations relating to:

• Programme Route and Route Date

• Programme Achievement and Exam Board Grade

• Dependants data

Drop‑down fields added to PLAQ reference data

If you manage PLAQ reference data, the Level and SSA Tier 2 fields now appear as drop‑down lists.

These drop‑downs display values held in reference data, making it easier to select valid options and ensuring greater consistency when maintaining PLAQ records.

General updates and changes

The following fields have been updated:

• When the qualification is in the PLAQ list, and you enter the qualification number for a UIO, the Qualification Level, Subject Code, and Qualification Aim fields automatically populate. This builds on earlier changes where other fields on the screen already populate automatically when you enter the qualification number.

• Reference data has been updated to reflect the changes from the 26/27 specification.

• The order of values in the Ethnicity reference data drop-down has been updated.

Automatic clearing of credit values for ineligible learners

You no longer need to manually remove tariff or planned credit values for learners who are not eligible for funding. The system now automatically sets these values to 0 in specific scenarios to ensure accurate FES outputs.

Credits cleared for non-qualifying learners

If you mark a learner as withdrawn, non-starter, or transferred before the funding qualifying date, the system now:

• Sets tariff and planned credit values to 0 in special details.

• Prevents these values from being included in the FES 2 output file.

• This ensures only eligible learners contribute to reported credits.

Credits cleared for self-financing learners (Source of Finance code 36)

When you set a learner’s source of finance to code 36 (self-financing), the system now:

• Automatically sets tariff and planned credits to 0 in special details.

• Ensures no ineligible credits are carried into FES 1 and FES 2 outputs.

This aligns with SFC requirements, as you cannot claim credits for self-funded learners.

Not applicable

Registration organisation field updates

The Registration organisation field has been added to the Curriculum Manager grid to support bulk editing. This field is also now available in clone and roll forward.

Note that the field has also been added to the webservices.

Not applicable

New reference data for the 26/27 ILR specification

The following screens have been added to reference data to meet the requirements of the 26/27 ILR specification:

• ILR Hours Record (HRSType)

• ILR Apprenticeship Price Reduction (AFin Type RIP)

Not applicable

Updated ILR field labels

We have updated the Include in ILR field labels across several areas of EBS to make their purpose clearer.

• Where the field controls ILR generation, it is now labelled Include in ILR Generation.

• Where the field controls ILR output, it is now labelled Include in ILR Output.

These changes appear across enrolments, curriculum, learner management, progress codes, and ILR manager screens. The underlying behaviour of the fields has not changed, only the labels have been updated to improve clarity.

Not applicable

Off The Job Planned Hrs Reduction — ILR Manager Aims Tab

A new column has been added to the ILR Manager Aims screen to capture reductions to off the job planned hours, with values kept in sync across the ILR Manager Aims tab and Enrolments Special Details screen.

• New editable column Off The Job Planned Hrs Reduction on the ILR Manager Aims tab, positioned between Fund Model and Planned Hours.

• Accepts integer values in the range 0–9999 (max 4 digits).

• Enrolment Special Details > Learner Manager Aims tab - updated values cascade through after ILR processing is run.

• Learner Manager Aims tab > Enrolment Special Details - Updated values cascade back when the Update Source function is used in ILR Manager.

Not applicable

Update Output Field Mapping for Hours Record Entity

As part of the 26/27 ILR changes, EBS has been updated to map existing data fields to the new Hours Record Entity in the ILR output. When a learner's ILR return is generated, EBS now evaluates each aim record's funding model, programme type, and aim type to automatically produce the correct Hours Record entries — no changes are required from users in how they enter data.

The following records will be produced in the Hours Record Entity based on the learner's aim data:

• HRS Code 1 - Populated from Planned Hours when Funding Model = 36 and Aim Type = 1

• HRS Code 2 - Populated from Planned Hours when Funding Model = 25, Programme Type = 31, and Aim Type = 1

• HRS Code 3 - Populated from Off The Job Actual Training Hours when Funding Model = 36 and Aim Type = 1

• HRS Code 4 - Populated from Off The Job Planned Hrs Reduction when Funding Model = 36 or Funding Model = 25 with Programme Type = 31, and Aim Type = 1

• HRS Code 5 - Populated from Planned Hours when Funding Model = 11 and Aim Type = 4

• HRS Code 6 - Populated from Additional Delivery Hours when Funding Model is 35, 38, or 81, and Aim Type = 4

All records in the Hours Record Entity will carry a Type of HRS, with the Hours Amount value taken directly from the corresponding EBS field as entered by the user.

Not applicable

Funding year 33 (2026/27) updates

EBS processes have been updated to support the requirements for the funding year 33 (2026/27) return.

When you generate an ILR return, the output now includes only the fields required by the 2026 to 2027 ILR specification, based on the learner’s funding model.

This update reflects recent changes to collection requirements, including where specific fields and entities are added or removed from the output. It helps ensure your ILR return meets statutory reporting requirements without including unnecessary data.

General updates and changes

The follow changes have been made:

• The Inst Comp Year field has been moved to the end of the ILR Manager HE grid.

  This field is no longer required for 2026/27 ILR output, in line with the latest ILR specification. Staff can still view the data for previous academic years where needed, but its new position helps distinguish historical reference data from fields required for current reporting.

• From funding year 33 onwards, the following hours fields are no longer included in the ILR output, in line with the 2026/27 ILR collection requirements:

  • Planned hours

  • Actual hours for off‑the‑job training

  • Additional delivery hours

• Completion of Year Instance fields have been removed from the ILR output so that to meet the 26/27 ILR collection requirements.

• The Special Defaults screen in reference data has been updated. The following fields are no longer visible to staff:

  • Funding Source 2

  • Delivery Mode

  • Main Delivery Method

  • Employer Role

  • Broker Contract Number

Not applicable

Update to LLWR Numeracy and Literacy reference data for 2026/27

The reference data for LLWR Level of Numeracy (LP34) and LLWR Level of Literacy (LP35) for the 2026/27 academic year has been updated as follows:

Updated the reference data values for:

• LLWR Level of Numeracy (LP34)

• LLWR Level of Literacy (LP35)

Reinstated the following fields in the LLWR output:

• StartNumeracy

• StartLiteracy

Not applicable

SDR reporting - Thesis in Te Reo Māori

Staff can now record when a learner’s thesis is written in Te Reo Māori.

A new Thesis in Te Reo Māori tick box is available in the Academic History tab for active learners in New Zealand. When this option is selected and the learner meets the required completion criteria, the SDR completion code in the Course Completion output file is reported as 8 instead of 2.

This update ensures thesis completions in Te Reo Māori are reported correctly for SDR submissions.

Manage academic history